Systems and methods for transaction pre authentication

ABSTRACT

Systems, methods, and computer-readable media are provided for mobile-based transaction pre-authorization. One example method comprises receiving, from a device (such as a mobile device), a pre-authorization request including at least selection of a payment method, and generating a pre-authorization for a purchase based on the selected payment method. The method further comprises receiving a transaction request, determining whether the received transaction request is associated with the pre-authorization, and processing the transaction request based on the determination. Systems and computer-readable media implementing the above method are also provided. User interfaces are also provided for enabling the use of such methods, systems, and computer-readable media on, for example, mobile devices.

RELATED APPLICATIONS

This application claims priority from U.S. Provisional Patent Application No. 62/017,486, filed on Jun. 26, 2014, which is hereby incorporated by reference in the present application.

BACKGROUND

Financial service providers regularly provide accounts to consumers that enable the consumers to purchase goods against a line of credit. The understanding with such accounts is that when the consumer makes an authorized purchase at a merchant, the financial service provider pays the merchant for the purchase, and the consumer will pay the financial service provider back at some point in the future. At times, however, consumers may lose their credit cards or otherwise lose control of their accounts, meaning that an unauthorized Individual could make fraudulent purchases using the account.

Often times, the risk of fraudulent transactions is borne by the financial service provider. Thus, many financial service providers have implemented fraud systems that attempt to determine whether a transaction is fraudulent. For example, if a financial service provider receives a $20.00 transaction request from a McDonald's in Arlington, Va. on Monday morning and also receives a $2,500.00 transaction request from a Home Plus store in Seoul, South Korea 20 minutes later, the financial service provider can deny one or both transaction requests because an authorized user cannot have traveled between both purchase locations in that short amount of time.

But most cases of fraud are not so obvious, and many fraud detection systems are known to have an unacceptably high false positive rate. Thus, transaction requests that are legitimate may be improperly denied. For example, if a consumer attempts to purchase a new television, the purchase may appear out of the ordinary when compared to the consumer's other purchases. The transaction may thus be denied even if the consumer has sufficient credit to make the purchase. This causes inconvenience for the consumer.

There is thus a need to address these and other issues. The present disclosure provides methods, systems, and computer-readable media to solve these and other issues.

SUMMARY

Disclosed embodiments include methods, systems, and computer-readable media configured to, for example, enable pre-authorization of transactions that might otherwise be denied as potentially fraudulent.

In one aspect, a method of pre-authorization is provided. The method comprises receiving, from a device, a pre-authorization request including at least selection of a payment method, and generating a pre-authorization for a purchase based on the selected payment method. The method further comprises receiving a transaction request, determining whether the received transaction request is associated with the pre-authorization, and processing the transaction request based on the determination. Systems and computer-readable media implementing the above method are also provided.

Aspects of the disclosed embodiments may include tangible computer-readable media that stores software instructions that, when executed by one or more processors, are configured to and capable of performing and executing one or more of the methods, operations, and the like consistent with the disclosed embodiments. Also, aspects of the disclosed embodiments may be performed by one or more processors configured as special-purpose processor(s) based on software instructions that are programmed with logic and instructions that perform, when executed, one or more operations consistent with the disclosed embodiments.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosed embodiments, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate disclosed embodiments and, together with the description, serve to explain the disclosed embodiments. In the drawings:

FIG. 1 is a block diagram of an exemplary system, consistent with disclosed embodiments.

FIG. 2 is a diagram of an exemplary electronic system, consistent with disclosed embodiments.

FIG. 3A is a diagram of an exemplary interface displaying choices of cards that a user can use in accomplishing a transaction request, consistent with disclosed embodiments.

FIG. 3B is a diagram of an exemplary interface requesting an approximate amount for a transaction request, consistent with disclosed embodiments.

FIG. 3C is a diagram of an exemplary interface displaying a confirmation that a pre-authorization request has been approved, consistent with disclosed embodiments.

FIG. 3D is a diagram of an exemplary interface displaying a denial of a pre-authorization request, consistent with disclosed embodiments.

FIG. 4A is a flowchart of an exemplary process for pre-authorizing a transaction request using a mobile device, consistent with disclosed embodiments.

FIG. 4B is a flowchart of an exemplary process for processing a transaction request initiated at a merchant system, consistent with disclosed embodiments.

DETAILED DESCRIPTION

Reference will now be made in detail to the disclosed embodiments, examples of which are illustrated in the accompanying drawings. Wherever convenient, the same reference numbers will be used throughout the drawings to refer to the same or like parts.

FIG. 1 is a block diagram of an exemplary system 100 for performing one or more operations consistent with the disclosed embodiments. In one embodiment, system 100 may include one or more financial service providers 110, one or more merchants 120, one or more mobile devices 130, and network 140. The components and arrangement of the components included in system 100 may vary. Thus, system 100 may include other components that perform or assist in the performance of one or more processes consistent with the disclosed embodiments.

Components of system 100 may be computing systems configured to provide systems and method for pre-authorizing a transaction request, consistent with disclosed embodiments. As further described herein, components of system 100 may include one or more computing devices (e.g., computer(s), server(s), etc.), memory storing data and/or software instructions (e.g., database(s), memory devices, etc.), and other known computing components. In some embodiments, the one or more computing devices may be configured to execute software instructions stored on one or more memory devices to perform one or more operations consistent with the disclosed embodiments. Components of system 100 may be configured to communicate with one or more other components of system 100, including systems associated with financial service provider 110, merchant 120, and/or mobile device 130. In certain aspects, users (e.g., user 135) may operate one or more components of system 100 to initiate and provide input for one or more operations consistent with the disclosed embodiments.

Financial service provider 110 may be an entity that provides, maintains, manages, or otherwise offers financial services. For example, financial service provider 110 may be a bank, credit card issuer, or any other type of financial service entity that generates, provides, manages, and/or maintains financial service accounts for one or more users. Financial service accounts may include, for example, credit card accounts, loan accounts, checking accounts, savings accounts, reward or loyalty program accounts, and/or any other type of financial service account known to those skilled in the art. Financial service provider system 110 may include infrastructure and components that are configured to generate and/or provide financial service accounts such as credit card accounts, checking accounts, debit card accounts, loyalty or reward programs, lines of credit, or the like. Consistent with certain disclosed embodiments, financial service provider 110, using financial service provider system 112, may provide manufacturer-based financial service accounts, which may be financial service accounts that are associated with a manufacturer of products or services, such as a merchant 120.

Financial service provider 110 may include one or more financial service provider systems 112. In one aspect, financial service provider system 112 may be one or more computing devices configured to perform one or more operations consistent with disclosed embodiments. In one aspect, financial service provider system 112 may be a desktop computer, a server, or any other type of computing device. Financial service provider system 112 may include one or more processors configured to execute software instructions stored in memory. The one or more processors may be configured to execute software instructions that when executed by a processor performs known Internet-related communication and financial service-based processes. For instance, financial service provider system 112 may execute software that provides data used for generating and displaying interfaces, including content on a display device included in, or connected to, mobile device 130. Financial service provider system 112 may also receive transaction requests from merchant 120 and/or network 140, and may send these transaction requests to fraud detection system 114 and/or card authorization system 116 for processing. Financial service provider system 112 may send responses to the received transaction requests to mobile device 130, merchant 120, and/or network 140.

Financial service provider 110 may include one or more fraud detection systems 114. In one aspect, fraud detection system 114 may be one or more computing devices configured to perform one or more operations consistent with disclosed embodiments. For example, fraud detection system 114 may be a desktop computer, a server, or any other type of computing device. Fraud detection system 114 may include one or more processors configured to execute software instructions stored in memory. The one or more processors may be configured to execute software instructions that when executed by the one or more processors perform methods that enable the detection of potentially fraudulent transaction requests. For instance, fraud detection system 114 may receive a transaction request from financial service provider system 112 or card authorization system 116 and may determine whether the received transaction request is potentially fraudulent.

Fraud detection system 114 may check the transaction request for fraudulence using known or as-yet-unknown processes—including those based on geographic location of merchant 120 or user 135, a dollar amount associated with the transaction request, a frequency or number of transaction requests associated with user 135, etc. Checking the transaction request may comprise generating a cumulative score relating to each transaction request and comparing it to one or more thresholds. For example, fraud detection system 114 may utilize three thresholds to determine fraudulence associated with a transaction request, such as a first threshold representing the highest possible score for a transaction request, a second threshold representing the lowest score at which a transaction request that is not pre-authorized (e.g., where no associated pre-authorization exists) can be approved, and/or a third threshold representing the lowest score at which a pre-authorized transaction request can be approved. So, for example, if a transaction request is pre-authorized using mobile device 130, then the transaction request may be approved if an associated score is lower than the first threshold and the second threshold but higher than the third threshold, while a transaction request that is not pre-authorized may only be approved if an associated score is lower than the first threshold but higher than the second threshold. In some embodiments, fraud detection system 114 may receive an indication from card authorization system 116 indicative of whether a received transaction request is associated with a pre-authorization request.

In addition, in some embodiments, fraud detection system 114 may check the transaction request for different characteristics based on whether the transaction request is associated with a pre-authorization. For example, fraud detection system 114 may perform one set of checks on transaction requests that are not associated with a pre-authorization, while fraud detection system 114 may perform only a subset of that set of checks on transaction requests that are associated with a pre-authorization.

Financial service provider 110 may include one or more card authorization systems 116. In one aspect, card authorization system 116 may be one or more computing devices configured to perform one or more operations consistent with disclosed embodiments. For example, card authorization system 116 may be a desktop computer, a server, or any other type of computing device. Card authorization system 116 may include one or more processors configured to execute software instructions stored in memory. The one or more processors may be configured to execute software instructions that when executed by the one or more processors perform methods that enable the processing of financial transaction authorization requests.

For instance, card authorization system 116 may receive a transaction request from fraud authorization system 114 and/or financial service system 112, and determine whether a received transaction request matches a pre-authorization. This comprises, for example, determining whether a transaction request includes a reference to a particular card or account and/or whether that particular card or account is associated with a pre-authorization. Determining whether a received transaction request is associated with a pre-authorization also comprises, in some embodiments, determining whether a dollar value associated with the pre-authorization is within some percentage (e.g., 10%) of a dollar value associated with the transaction. Card authorization system 116 may also communicate to fraud detection system 114 whether or not a transaction request is associated with a previously-requested pre-authorization and/or should be authorized.

In some embodiments, one or both of fraud detection system 114 and card authorization system 116 may be configured to require that a transaction request be associated with a pre-authorization before approving the transaction request. In other embodiments, one or both of fraud detection system 114 and card authorization system 116 may be configured to require that transaction requests of a certain type (e.g., above a certain associated dollar value, at a particular merchant, associated with particular goods or services, or when merchant 120 or user 135 is in a particular geographic location) be associated with a pre-authorization before approval.

Merchant 120 may be an entity that offers goods, services, and/or information, such as a retailer (e.g., Macy's®, Target®, Amazon.com®, etc.), grocery store, service provider (e.g., utility company, etc.), or any other type of entity that offers goods, services, and/or information that consumers (e.g., end-users or other business entities, such as user 135) may purchase, consume, use, etc. Merchant 120 may offer for sale one or more products of product manufacturer 120. In one example, merchant 120 may be associated with a brick and mortar retail location. In another example, merchant 120 may comprise an online merchant that sells goods through the Internet or another network (such as network 140). Merchant 120 may also include back- and/or front-end computing components that store data and execute software instructions to perform operations consistent with disclosed embodiments, such as computers that are operated by employees of the merchant (e.g., back office systems, etc.).

Merchant 120 may include merchant system 122. Merchant system 122 may include one or more computing systems, such as server(s), desktop computers, etc., that are configured to execute stored software instructions to perform operations associated with a merchant, including one or more processes associated with processing purchase transaction requests, generating transaction request data, generating product data (e.g., SKU data) relating to transaction requests, etc. Merchant system 122 may perform one or more operations consistent with the disclosed embodiments. In one example, merchant system 122 may comprise a point-of-sale device (for example, at a brick and mortar location). In another example, merchant system 122 is a web site operated by or on behalf of merchant 120 that enables a consumer (e.g., user 135) to receive information about goods or services for sale and initiate a purchase for those goods or services. The disclosed embodiments are not limited to any particular configuration of merchant system 122.

Mobile device 130 may be one or more computing devices configured to perform one or more operations consistent with disclosed embodiments. in one example, mobile device 130 may be a tablet, a smart phone, a cellular phone, a personal digital assistant (PDA), a media device (such as an iPod®), or any other type of computing device. As mentioned herein, however, the disclosed embodiments are not limited to such examples.

Mobile device 130 may include one or more processors configured to execute software instructions stored in memory, such as memory included in mobile device 130. Mobile device 130 may include software that when executed by a processor performs known Internet-related communication, content display processes, and financial service-related processes for a user of mobile device 130. For instance, mobile device 130 may execute browser or related mobile display software that generates and displays interfaces including content on a display device included in, or in communication with, mobile device 130. Mobile device 130 may execute applications and/or communication software that allows mobile device 130 to communicate with components over network 140, and generates and displays content in interfaces via a display device included in mobile device 130. The disclosed embodiments are not limited to any particular configuration of mobile device 130. In some embodiments, mobile device 130 may be configured to execute software instructions relating to location services, such as determining a location using GPS or Wi-Fi® networks. For example, mobile device 130 may be configured to determine a geographic location of mobile device 130 (and associated user 135) and provide corresponding location data and time stamp data.

In some embodiments, mobile device 30 is configured to interact with merchant 120 or merchant system 122 to effect a pre-authorization or transaction request. This includes, for example, user 135 operating mobile device 130 to browse a website hosted by merchant 120, mobile device 130 communicating card information to merchant system 122, or the like.

Network 140 may be any type of network configured to provide communications between components of system 100. For example, network 140 may be any type of network (including infrastructure) that provides communications, exchanges information, and/or facilitates the exchange of information, such as the Internet, a Local Area Network, Near-Field Communication (NFC), Bluetooth, Optical code scanner, or other suitable connection(s) that enables the sending and receiving of information between the components of system 100. In other embodiments, one or more components of system 100 may communicate directly through a dedicated communication link(s), such as links between financial service provider 110, merchant 120, and/or mobile device 130.

It is to be understood that the configuration and boundaries of the functional building blocks of system 100 have been defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. For example, financial service provider system 112 and merchant system 122 may constitute a part of components of system 100 other than those specifically described, or may constitute a part of multiple components of system 100 (i.e., a distributed system).

FIG. 2 shows an exemplary electronic system 200 consistent with disclosed embodiments. Variations of exemplary system 200 may be used to implement portions or all of financial service provider 110, merchant 120, and/or mobile device 130. In one embodiment, system 200 may comprise one or more processors 221, one or more input/output (I/O) devices 222, and one or more memories 223. In some embodiments, system 200 may take the form of a server, general purpose computer, mainframe computer, or the like. In some embodiments, system 200 may take the form of a mobile computing device such as a smartphone, tablet, laptop computer, or the like. Alternatively, system 200 may be configured as a particular apparatus, embedded system, dedicated circuit, or the like, based on the storage, execution, and/or implementation of the software instructions that perform one or more operations consistent with the disclosed embodiments.

Processor(s) 221 may include one or more known processing devices, such as mobile device microprocessors, desktop microprocessors, server microprocessors, or the like. The disclosed embodiments are not limited to a particular type of processor.

Memory 223 may include one or more storage devices configured to store instructions usable by processor 221 to perform functions related to the disclosed embodiments. For example, memory 223 may be configured with one or more software instructions, such as program(s) 224 that perform one or more operations when executed by processor 221. The disclosed embodiments are not limited to separate programs or computers configured to perform dedicated tasks. For example, memory 223 may include a single program or multiple programs that perform the functions of mobile device 130. Memory 223 may also store data 225 that is used by one or more programs 224.

In certain embodiments, memory 223 may store software executable by processor(s) 221 to perform one or more methods, such as the methods associated with user interfaces in FIGS. 3A-3C and/or the methods represented by the flowcharts depicted in FIGS. 4A and 4B.

I/O devices 222 may be one or more devices configured to allow data to be received and/or transmitted by system 200. I/O devices 222 may include one or more digital and/or analog devices that allow system 200 to communicate with other machines and devices, such as other components of system 100. For example, I/O devices 222 may include a screen for displaying messages to user 135. I/O devices 222 may also include one or more digital and/or analog devices that allow a user to interact with system 200 such as a touch-sensitive area, keyboard, buttons, or microphones. I/O devices 222 may also include other components known in the art for interacting with a user. I/O devices 222 may also include one or more hardware/software components for communicating with other components of system 100. For example, I/O devices 222 may include a wired network adapter, a wireless network adapter, a cellular network adapter, or the like. Such network components enable system 200 to communicate with other systems to send and receive data.

The components of system 200 may be implemented in hardware, software, or a combination of both hardware and software, as will be apparent to those skilled in the art. For example, although one or more components of system 200 may be implemented as computer processing instructions, all or a portion of the functionality of system 200 may be implemented instead in dedicated electronics hardware.

FIG. 3A is a diagram of an exemplary interface 310 displaying choices of cards that a user can use in accomplishing a pre-authorization request. In exemplary FIG. 3A, interface 310 is depicted as being displayed on mobile device 130 as part of a mobile wallet application. It is to be understood, however, that not all embodiments require interface 310 to be implemented as part of a mobile wallet application. For example, interface 310 can be displayed on mobile device 130, a personal computer, or the like, as part of a web site hosted by financial service provider system 112.

Mobile device 130 may present interface 310 to user 135, enabling user 135 to select which card will be used in an upcoming transaction. Cards 320A-320D may constitute credit cards, debit cards, charge cards, other payment cards, stored value cards, or other cards. In alternative embodiments, cards 320A-320D may include non-card accounts as well, including charge accounts, checking accounts, savings accounts, lines of credit, or the like.

In some embodiments, mobile device 130 may present interface 310 to user 135 when user 135 opens the mobile wallet application, opens another application, opens a web site to select a card, and/or performs some other action that indicates that user 135 may desire to make a purchase.

User 135 may select one of cards 320A-320D by actuating the selected card (e.g., by pressing on a screen on mobile device 130 or moving a keypad to select the desired card). Interface 310 may then receive a press at button 330 to select that card for the transaction. In some embodiments, after receiving a press at button 330, the next interface shown on mobile device 130 may include another interface, such as the interface depicted in FIG. 3B, while in other embodiments, the next interface shown on mobile device 130 may be the interface depicted in FIG. 3C.

FIG. 3B is a diagram of an exemplary interface 311 requesting an approximate amount for a pre-authorization request, consistent with disclosed embodiments. In exemplary FIG. 3B, interface 311 is depicted as being displayed on mobile device 130 as part of a mobile wallet application. It is to be understood, however, that not all embodiments require interface 311 to be implemented as part of a mobile wallet application. For example, interface 311 can be displayed on mobile device 130, a personal computer, or the like, as part of a web site hosted by financial service provider system 112. According to some embodiments, mobile device 130 may further present an interface (not shown) requesting an indication of the merchant with which user 135 intends to complete a transaction and/or a location (e.g., a zip code, location, or website) where user 135 intends to complete the transaction.

In some embodiments, interface 311 may be presented to user 135 after user 135 has selected a card 320A-320D and pressed button 330, as shown in FIG. 3A. Interface 311 may include a dollar field 340, a set of up arrows 341, a set of down arrows 342, a submit button 360, and/or a back button 361.

Interface 311 may receive a selection from user 135 regarding an approximate amount for an upcoming transaction request. While in some situations user 135 will not know an exact amount of an upcoming transaction (because of, for example, tax or shipping and handling), user 135 may be able to guess within 10% of the actual amount for the transaction. Thus, in some embodiments, interface 311 may provide up arrows 341 and down arrows 342 to enable user 135 to select an approximate dollar amount within, for example, 10% of the actual amount of an upcoming transaction. In other embodiments, interface 311 may receive inputted digits in dollar field 340 to indicate approximately how much user 135 believes the transaction will be. Upon receipt of a button press at button 360, mobile device 130 may send the card selected in FIG. 3A (e.g., one of cards 320A-320D) and the value in dollar field 340. Alternatively, interface 311 may receive a button press at button 361, if, for example, user 135 selected an incorrect card from cards 320A-320D and desires to select a different card. Pressing button 361, in some embodiments presents interface 310 in FIG. 3A to user 135.

FIG. 3C is a diagram of an exemplary interface 312 displaying a confirmation that a pre-authorization request has been approved, consistent with disclosed embodiments. In exemplary FIG. 3C, interface 312 is depicted as being displayed on mobile device 130 as part of a mobile wallet application. It is to be understood, however, that not all embodiments require interface 312 to be implemented as part of a mobile wallet application. For example, interface 312 can be displayed on mobile device 130, a personal computer, or the like, as part of a web site hosted by financial service provider system 112.

In some embodiments, interface 312 may be presented to user 135 after user 135 has selected a card 320A-320D and pressed button 330, as shown in FIG. 3A. In other embodiments, interface 312 may be presented to user 135 after user 135 has selected a card as in FIG. 3A and/or input an approximate dollar value in dollar field 340 as shown in FIG. 3B. Interface 312 may include confirmation 370 and button 371.

Confirmation 370 may serve to inform user 135 that a pre-authorization request has been approved. This may give user 135 confidence that a future transaction corresponding to the parameters associated with the pre-authorization request (e.g. the particular card selected and/or a dollar value specified) will be approved, which may serve to prevent denial of a transaction that would otherwise appear potentially fraudulent. Confirmation 370 may also include validity period, which indicates how long the approval is valid for.

FIG. 3D is a diagram of exemplary interface 313 displaying a denial of a pre-authorization request, consistent with disclosed embodiments. In exemplary FIG. 3D, interface 313 is depicted as being displayed on mobile device 130 as part of a mobile wallet application. It is to be understood, however, that not all embodiments require interface 313 to be implemented as part of a mobile wallet application. For example, interface 313 can be displayed on mobile device 130, a personal computer, or the like, as part of a web site hosted by financial service provider system 112.

In some embodiments, interface 313 may be presented to user 135 have user 135 has selected a card 320A-320D and pressed button 330, as shown in FIG. 3A. In other embodiments, interface 313 may be presented to user 135 after user 135 has selected a card as in FIG. 3A and/or input an approximate dollar value in dollar field 340 as shown in FIG. 3B. Interface 313 may include denial 380 and button 381.

Denial 380 may serve to inform user 135 that a pre-authorization request has been denied. Denial of a pre-authorization request could occur because an approximate dollar value associated with the pre-authorization request exceeds a pre-set amount associated with the card or account, because a transaction with the approximate dollar amount would exceed a credit limit associated with the card or account, because the card or account is dosed or suspended, because the pre-authorization request appears fraudulent, or the like. According to some embodiments, denial 380 may further provide one or more reason(s) why the pre-authorization request was denied (e.g., the pre-authorization request indicated a dollar amount that would exceed the credit limit associated with the card or account, the card has been reported as stolen or missing, and/or any other factor capable of raising the risk of fraud, default, etc.).

In some embodiments, denial 380 may inform user 135 that further authorization is required from user 135. For example, if a pre-authorization request appears fraudulent, interface 313 may present button to enable user 135 to provide further information in order to authenticate the pre-authentication request. Interface 313 may receive a press at button 381 and proceed to a new interface (not pictured) to receive further authentication from user 135, such as a password, a PIN, biometric identification, or the like. In other embodiments, denial 380 may present a phone number which, if dialed by user 135, connects user 135 to a pre-recorded message informing user 135 why the pre-authorization request was denied and/or connects user 135 to a live operator that can assist the user in obtaining a confirmation for the pre-authorization request.

FIG. 4A is a flowchart of an exemplary process 400 for pre-authorizing a transaction request. In step 401, an application (such as a mobile wallet application or web site) may be initialized by mobile device 130. Mobile device 130, in step 403, may prompt user 135 to select a card or account with which user 135 is intending on making a purchase via, for example, interface 310 in FIG. 3A. As explained above with reference to FIG. 3A, mobile device 130 may present a set of cards and may receive a selection of at least one of those cards (or accounts) for use with an upcoming transaction.

In step 404, mobile device 130 may prompt user 135 to input an approximate amount for the upcoming transaction. As explained above with reference to FIG. 3B, the approximate amount may be received in a variety of input means. After inputting the approximate amount, process 400 may continue to step 405. Step 404, however is optional and may not be executed in all embodiments. In those embodiments, process 400 can proceed directly from step 403 to 405.

After prompting user 135 to select a card or account (step 403) and/or prompting user 135 to input an approximate amount for the upcoming transaction (step 404), in step 405, mobile device 130 may generate a pre-authorization request for sending to card authorization system 116. The pre-authorization request may include the selected card or account (from step 403), an approximate amount for the upcoming transaction (from step 404), and/or a location of mobile device 130 (e.g., a geographic location such as latitude or longitude coordinates or an address). Mobile device 130 may also send that pre-authorization request to card authorization system 116.

In step 407, card authorization system 116 may receive the pre-authorization request. In step 409, card authorization system 116 may perform a set of validity checks on the received pre-authorization request. For example, card authorization system 116 may attempt to verify the identity of user 135 or mobile device 130, may examine the pre-authorization request for data transmission or security issues, may determine whether the card or account referenced in the pre-authorization request is in good standing (e.g., not overdrawn, unpaid, or charged off), may determine whether the dollar value referenced in the pre-authorization request would cause the card or account to exceed a credit limit, or the like.

If card authorization system 116 determines that the pre-authorization request is valid and should be granted, then in step 411, card authorization system 116 may generate a pre-authorization for sending to mobile device 130. The pre-authorization includes, for example, an approval number that indicates to mobile device 130 and user 135 that the pre-authorization request was granted. In some embodiments, pre-authorizations are also associated with a time stamp that indicates a validity period, after which the pre-authorization will “expire” and no longer be valid. So, if a transaction request is received and an associated pre-authorization has expired, the transaction request will not be determined to be “associated” with that pre-authorization.

Card authorization system 116 may send an indication of the pre-authorization to mobile device 130. In step 413, mobile device 130 may receive the pre-authorization. Mobile device may, as explained above with reference to FIG. 3C, present an indication to user 135 that the pre-authorization was received. This gives user 135 confidence that a transaction in line with the parameters associated with the pre-authorization request sent in step 405 will be approved, which may serve to prevent denial of a transaction even if the transaction otherwise appears potentially fraudulent.

FIG. 4B is a flowchart of an exemplary process 410 for processing a transaction request initiated at merchant system 122. In step 421, merchant system 122 may initialize a transaction. This may comprise, for example, receiving physical items from user 135 for scanning at a physical point-of-sale device, determining items added to an online shopping cart by user 135, or the like. Step 421 may also comprise receiving a card or account identifier that user 135 wishes to use to pay for the transaction. This includes, for example, receiving a physical payment card and swiping it through a magnetic swipe reader, receiving an NFC-based communication that includes a payment card number, receiving an a card number entered by user 135 on a web site associated with merchant device 122, or the like.

In step 423, merchant system 122 may generate a transaction request and send it to financial service provider system 112. The transaction request may include a card or account that user 135 is attempting to use to effect the transaction, a dollar values associated with the transaction, a location of merchant 122 (e.g., a geographic location such as latitude and longitude coordinates or a street address, and other information as necessary (e.g., authentication information). In step 425, financial service provider 112 may receive the transaction request and forward it to the appropriate subsystem, e.g., card authorization system 116.

In step 427, card authorization system 116 may determine whether the received transaction is associated with a pre-authorization. Card authorization system 116 may determine that a transaction is associated with a pre-authorization if, for example, the received transaction includes a reference to a card or account that is associated with a pre-authorization.

Determining that a received transaction is associated with a pre-authorization may also comprise, in some embodiments, determining whether a dollar value associated with the received transaction is within some percentage of a dollar value associated with a pre-authorization. As one example, card authorization system 116 may determine that a received transaction is only associated with a pre-authorization if the received transaction references a card also referenced by the pre-authorization and is within 15% of a dollar value associated with the pre-authorization. Otherwise, card authorization system 116 may determine that the received transaction is not associated with that pre-authorization. As another example, card authorization system 116 may determine that a received transaction is only associated with a pre-authorization if the transaction is within some percentage of a dollar value associated with the pre-authorization, the percentage being based on the amount of the pre-authorization. For example, a pre-authorization for less than $1,000.00 would be associated with a transaction if the transaction and pre-authorization differed by less than 10%, while a pre-authorization for more than $1,000.00 would be associated with a transaction if the transaction and pre-authorization differed by less than 5%.

Determining that a received transaction is associated with a particular pre-authorization may also comprise, in some embodiments, determining whether the current date and time are within a validity period associated with the pre-authorization. For example, the pre-authorization may be associated with a 30-minute or one-day window during which transaction requests can be “associated” with the pre-authorization. Conversely, if the transaction request is received outside of that window, card authorization system 116 may determine that the transaction request is not associated with the pre-authorization.

Determining that a received transaction is associated with a particular pre-authorization may also comprise, in some embodiments, determining whether a location of merchant 122 included in the transaction request is within some distance of a location of mobile device 130 associated with the pre-authorization.

In some embodiments, step 427 may also comprise card authorization system 116 determining whether the card or account referenced in the transaction is in good standing (e.g., not overdrawn, unpaid, or charged off), determining whether the dollar value referenced in the transaction would cause the card or account to exceed a credit limit, or the like. (Card authorization system 116 may be configured in these embodiments to send an indication to financial service provider system 112 indicating that the transaction should be denied.)

In situations where a received transaction is not associated with a pre-authorization, card authorization system 116 may send the transaction to fraud detection system 114 with an indication that it is not associated with a pre-authorization. In step 429, fraud detection system 114 may determine whether the transaction passes fraud checks. This includes, for example, determining whether the transaction is an outlier from previous transactions (e.g., is received from a merchant that user 135 does not frequent, is received from a merchant in a geographic area that user 135 is not known to frequent, contains a dollar value significantly higher than other transactions associated with user 135) or otherwise appears fraudulent.

In some embodiments determining whether a transaction passes fraud checks comprises fraud detection system 114 generating a cumulative score associated with the transaction. For example, a cumulative score associated with the transaction may be based on a multitude of aspects associated with the transaction, each aspect being associated with a score reflective of whether that aspect indicates that the transaction request is fraudulent. Example aspects include a number of transactions performed in the past 24 hours, a distance between a location associated with a current transaction request and the last five transactions, a difference in dollar value between this transaction and the previous 10 transactions, or the like. In some embodiments, the more likely that a particular aspect is to make the transaction appear fraudulent, the higher a score associated with the aspect. The scores associated with each aspect may then be added together to obtain the cumulative score. A higher cumulative score may represent a greater likelihood that the associated transaction is fraudulent. For example, a score between 0 and 500 may be considered as “not likely fraudulent,” a score of 501 to 1000 may be considered as “likely fraudulent,” and a score above 1000 may be considered as “fraudulent.” (It is to be understood, however, that not all embodiments require these particular scores.)

If fraud detection system 114 generates a score associated with a transaction and determines that the score is outside of an acceptable range (e.g., higher than a range of scores associated with “not likely fraudulent” transactions), fraud detection system 114 may determine that the transaction is likely fraudulent and should be denied, and forwards the transaction with that indication to financial service provider system 112. For example, if the transaction is not associated with a pre-authorization, fraud detection system may determine that the transaction is likely fraudulent if an associated score is 501 or above. Financial service provider system 112 may generate a denial (step 431) and send it to merchant system 112, which receives the denial in step 435. (User 135 can then be informed that the transaction was denied, and can retry the transaction, contact financial service provider 110, or take other actions.)

If, on the other hand, the cumulative score generated by fraud detection system 114 is within an acceptable range (e.g., between 1 and 500), fraud detection system 114 may determine that the transaction is not likely to be fraudulent and should be approved, and forwards the transaction with an indication that it should be approved to financial service provider system 112. Financial service provider system 112 may generate an approval (step 433) and send it to merchant system 112, which receives it in step 435.

If, however, in step 427, card authorization system 116 determines that a received transaction is associated with a pre-authorization, then, in some embodiments, card authorization system 116 may determine that the transaction should be approved. Card authorization system 116 may forward the transaction with an indication that it should be approved to financial service provider system 112. Financial service provider system 112 may generate an approval (step 433) and send it to merchant system 112, which receives it in step 435.

In some embodiments, however, if card authorization system 116 determines that a received transaction is associated with a pre-authorization, card authorization system 116 sends an indication to fraud detection system 114 to perform fraud checks on the transaction. Fraud detection system 114 may perform a set of validity checks on transactions that are not associated with a pre-authorization, while fraud detection system 114 may perform only a subset of those validity checks on transactions that are associated with a pre-authorization. In other embodiments, fraud detection system 114 may generate a cumulative score associated with the transaction and determine that the transaction is not fraudulent so long as the cumulative score is not higher than some threshold (e.g., higher than a range of scores associated with “fraudulent” transactions).

The foregoing description has been presented for purposes of illustration. It is not exhaustive and is not limited to the precise forms or embodiments disclosed. Modifications and adaptations of the embodiments will be apparent from consideration of the specification and practice of the disclosed embodiments. For example, the described implementations include hardware and software, but systems and methods consistent with the present disclosure can be implemented as hardware alone. Furthermore, although aspects of the disclosed embodiments are described as being associated with data stored in memory and other tangible computer-readable storage mediums, one skilled in the art will appreciate that these aspects can also be stored on and executed from many types of tangible computer-readable media, such as secondary storage devices, like hard disks, floppy disks, or CD-ROM, or other forms of RAM or ROM.

Computer programs based on the written description and methods of this specification are within the skill of a software developer. The various programs or program modules can be created using a variety of programming techniques. For example, program sections or program modules can be designed in or by means of Java, C, C++, assembly language, Perl, PHP, HTML, or other programming languages. One or more of such software sections or modules can be integrated into a computer system, computer-readable media, or existing communications software.

Moreover, while illustrative embodiments have been described herein, the scope includes any and all embodiments having equivalent elements, modifications, omissions, combinations (e.g., of aspects across various embodiments), adaptations or alterations based on the present disclosure. The elements in the claims are to be interpreted broadly based on the language employed in the claims and not limited to examples described in the present specification or during the prosecution of the application, which examples are to be construed as non-exclusive. Further, the steps of the disclosed methods can be modified in any manner, including by reordering steps or inserting or deleting steps. It is intended, therefore, that the specification and examples be considered as example only, with a true scope and spirit being indicated by the following claims and their full scope of equivalents. 

1. A system comprising a mobile device and an authorization system, wherein the mobile device comprises: at least one processor; a display device; and a storage medium comprising instructions that when executed cause the at least one processor to perform a method comprising: presenting at least one interface on the display device requesting input of a payment method and an amount of an upcoming transaction; receiving, as input, a selection of a payment method and the amount; generating, based on the input, a pre-authorization request for sending to the authorization system; and sending, over a network, the pre-authorization request; and wherein the authorization system comprises: at least one processor; and a storage medium comprising instructions that when executed cause the at least one processor to perform a method comprising: receiving, from the mobile device, the pre-authorization request; generating a pre-authorization based on the pre-authorization request; receiving, over a network, a transaction request; determining whether the received transaction request is associated with the pre-authorization; and processing the transaction request based on the determination.
 2. The system of claim 1, wherein receiving the transaction request comprises receiving the transaction request from the mobile device.
 3. The system of claim 1, wherein: the pre-authorization request includes a location associated with the mobile device; and determining whether the received transaction request is associated with the pre-authorization comprises determining a distance between the location in the pre-authorization request and a location associated with the transaction request.
 4. A method of pre-authorization, comprising the following steps performed on a mobile device: presenting, on a display device of the mobile device, at least one interface, the at least one interface requesting input of: a payment method, and an estimated amount of an upcoming transaction; receiving, as input, a selection of a payment method and the amount; determining a location of the mobile device; generating a pre-authorization request for sending to the authorization system, the request comprising the payment method, the amount, and the determined location; and sending, over a network, the pre-authorization request.
 5. A computer-implemented method, comprising; receiving, from a device, a pre-authorization request including at least selection of a payment method; generating a pre-authorization for a purchase based on the selected payment method; receiving, over a network, a transaction request; determining whether the received transaction request is associated with the pre-authorization; and processing the transaction request based on the determination.
 6. The method of claim 5, wherein: receiving a selection of a payment method further comprises receiving a dollar amount indicating an approximate purchase price associated with a future transaction request, and determining whether the received transaction request is associated with the pre-authorization comprises determining whether the dollar amount differs from a dollar amount associated with the transaction request by less than a predetermined dollar amount.
 7. The method of claim 5, wherein processing the transaction request further comprises: determining a first threshold and a second threshold, wherein a score less than the first threshold represents a transaction that is not likely to be fraudulent, a score between the first threshold and second threshold represents a transaction that is likely fraudulent, and a score above the second threshold is fraudulent; generating a cumulative fraud score related to the transaction request; when it is determined that the received transaction request indicates the use of the selected card: approving the transaction request when the fraud score is below the second threshold, and denying the transaction request when the fraud score is above the second threshold; and when it is determined that the received transaction request does not indicate the use of the selected card, then: approving the transaction request when the fraud score is below the first threshold, and denying the transaction request when the fraud score is above the first threshold.
 8. The method of claim 5, wherein determining whether the received transaction request is associated with the pre-authorization comprises determining whether the transaction request and the pre-authorization refer to the same payment method.
 9. The method of claim 5, wherein the payment method comprises at least one of a financial card or an account.
 10. A system, comprising; at least one processor; and memory comprising instructions configured to, when executed by the at least one processor, perform a method comprising: receiving a pre-authorization request including at least selection of a payment method; generating a pre-authorization for a purchase based on the selected payment method; receiving a transaction request; determining whether the received transaction request is associated with the pre-authorization; and processing the transaction request based on the determination.
 11. The system of claim 10, wherein: receiving a selection of a payment method further comprises receiving a dollar amount indicating an approximate purchase price associated with a future transaction request, and determining whether the received transaction request is associated with the pre-authorization comprises determining whether the dollar amount differs from a dollar amount associated with the transaction request by less than a predetermined dollar amount.
 12. The system of claim 10, wherein processing the transaction request further comprises: determining a first threshold and a second threshold, wherein a score less than the first threshold represents a transaction that is not likely to be fraudulent, a score between the first threshold and second threshold represents a transaction that is likely fraudulent, and a score above the second threshold is fraudulent; generating a cumulative fraud score related to the transaction request; when it is determined that the received transaction request indicates the use of the selected card: approving the transaction request when the fraud score is below the second threshold, and denying the transaction request when the fraud score is above the second threshold; and when it is determined that the received transaction request does not indicate the use of the selected card, then: approving the transaction request when the fraud score is below the first threshold, and denying the transaction request when the fraud score is above the first threshold.
 13. The system of claim 10, wherein determining whether the received transaction request is associated with the pre-authorization comprises determining whether the transaction request and the pre-authorization refer to the same payment method.
 14. The system of claim 10, wherein the payment method comprises at least one of a financial card or an account.
 15. A computer-readable medium comprising instructions, the instructions configured to cause at least one processor to perform a method comprising: receiving, from a device, a pre-authorization request including at least selection of a payment method; generating a pre-authorization for a purchase based on the selected payment method; receiving a transaction request; determining whether the received transaction request is associated with the pre-authorization; and processing the transaction request based on the determination.
 16. The medium of claim 16, wherein: receiving a selection of a payment method further comprises receiving a dollar amount indicating an approximate purchase price associated with a future transaction request, and determining whether the received transaction request is associated with the pre-authorization comprises determining whether the dollar amount differs from a dollar amount associated with the transaction request by less than a predetermined dollar amount.
 17. The medium of claim 16, wherein processing the transaction request further comprises: determining a first threshold and a second threshold, wherein a score less than the first threshold represents a transaction that is not likely to be fraudulent, a score between the first threshold and second threshold represents a transaction that is likely fraudulent, and a score above the second threshold is fraudulent; generating a cumulative fraud score related to the transaction request; when it is determined that the received transaction request indicates the use of the selected card: approving the transaction request when the fraud score is below the second threshold, and denying the transaction request when the fraud score is above the second threshold; and when it is determined that the received transaction request does not indicate the use of the selected card, then: approving the transaction request when the fraud score is below the first threshold, and denying the transaction request when the fraud score is above the first threshold.
 18. The medium of claim 16, wherein determining whether the received transaction request is associated with the pre-authorization comprises determining whether the transaction request and the pre-authorization refer to the same payment method.
 19. The medium of claim 16, wherein the payment method comprises at least one of a financial card or an account. 